##[group]The deploy tool's tests
npm run test:deploy
##[endgroup]
shell: bash -e /home/runner/_temp/18de4eaeb8f0ec74.sh

> test:deploy
> node --test "scripts/deploy/*.test.mjs"

error: no matching package named `base64` found
location searched: crates.io index
required by package `g1t-api v0.1.0 (/home/runner/work/repo/apps/api)`
note: offline mode (via `--offline`) can sometimes cause surprising resolution failures
help: if this error is too confusing you may wish to retry without `--offline`
✔ the manifest matches every wrangler config in the repository (182.33701ms)
✔ every wrangler.jsonc is found, and only checked-in ones (96.66632ms)
✔ problems are found: an unlisted config, a later-stage binding, a wrong database, an unnamed KV (117.31903ms)
✔ stages follow bindings: nothing binds to a unit that ships after it (2.51573ms)
✔ inside a stage, a Worker that does not exist yet goes before those bound to it (1.65604ms)
✔ Rust workers build with the shared script and the same wasm-opt level (2.45365ms)
✔ shared crates and packages are read from workspace metadata (1.02636ms)
✔ the runner's image is built from the runner crate and what it uses, on the base its lock names (2.0092ms)
✔ services/runner/base.json records the base its folder builds (72.07828ms)
✔ an image's hash ignores line endings, and its tags say what they are (331.86295ms)
✔ only the lockfile entries the runner is built from name its image (1.32468ms)
✔ the runner's deploy config names its image by reference, beside its wrangler.jsonc (91.50789ms)
✔ the registry is asked for an image's manifest, without Docker (2.17874ms)
✔ a push counts only when it ends with a digest, and is tried again (2.15453ms)
✔ a static Linux binary is told from a dynamic one (2.81732ms)
﹣ path dependencies agree with Cargo's own resolved graph (3155.49125ms) # cargo metadata could not resolve offline
✔ every import that leaves a unit's folder is covered by its dependencies or inputs (536.20945ms)
✔ a shared crate's change reaches every unit built from it, and no other (3.28657ms)
✔ a shared package's change reaches what imports it (0.63558ms)
✔ a crate's tests, benches and examples deploy nothing (2.99273ms)
✔ a Rust file compiled only for tests is found from what declares it (56.52923ms)
✔ this repository's test-only sources are read from git (2401.26029ms)
✔ decide: a change only to tests deploys nothing (4.34892ms)
✔ own folders, declared inputs and root files (3.19736ms)
✔ a Cargo.lock change reaches only crates that use what changed (2.67105ms)
✔ a package-lock change reaches through workspace links (1.41907ms)
✔ decide: changed units deploy, others wait, unknown ones deploy (0.67371ms)
✔ decide: --force deploys unchanged units; a commit missing from history deploys (0.32559ms)
✔ decide: Cargo.lock counts only where it reaches (1.23524ms)
✔ decide: the runner's image rebuilds only when what it is built from changed (1.14405ms)
✔ the plan as data: migrations, and each stage's units in jobs that share a build (4.73628ms)
✔ units are picked by short name, folder or Worker name (1.45967ms)
✔ a CI job installs only what its units need (3.25152ms)
✔ a deploy is annotated with its commit, and read back (0.83792ms)
✔ the live commit: the live version's, looking through secret changes (0.98781ms)
✔ Wrangler's output: pending migrations and the version a deploy made (1.3776ms)
✔ the API's answers: the live commit as Wrangler's would give it (2.74041ms)
✔ the API's answers: a Worker never deployed, and a refusal, never throw (503.85314ms)
✔ the API is used only with the token Wrangler would be given (1.01388ms)
✔ pending migrations: the folder's files less the names in d1_migrations (3.01266ms)
✔ the pool runs everything, no more than its limit at once (17.11147ms)
✔ self-hosting builds every Rust service the manifest says it runs (1.04123ms)
✔ the self-hosting architecture page names every unit (0.71537ms)
✔ resolveStack works on a manifest with no workspace crates or packages (6.64897ms)
✔ decide: a commit older than what runs is never deployed by accident, even forced; --rollback means it (0.59363ms)
✔ a deploy by hand reports to the repository on g1t, and a workflow's does not (2.90491ms)
✔ webhooks: the hourly purge deletes old deliveries by time (5.1447ms)
✔ billing: this month's users are read from an index, not the ledger (128.28202ms)
✔ events: a repository's events of one type, newest first, page by page (4.97049ms)
✔ actions: a self-hosted runner's poll finds queued jobs by namespace, whatever its case (20.71008ms)
✔ chat: a channel's messages and a thread's replies, newest first, page by page (4.21708ms)
✔ chat: the sidebar's unread messages are read from each channel's index, after the last read (54.19738ms)
✔ chat: a page's reactions are read by message, and a workspace's emoji by name (5.81947ms)
scheduler: g1t-webhooks (* * * * *) is still running from the last time; skipped
scheduler: g1t-webhooks (* * * * *): 200 {"outcome":"exception"}
✔ fields read numbers, ranges, lists and steps (3.81448ms)
✔ the services' crons match when hosted g1t's would fire (3.79384ms)
✔ what is due is each matching cron of each service (1.02093ms)
✔ a run asks Wrangler for the handler, and a slow one is not doubled (181.43821ms)
✔ a deploy is announced to status.g1t.sh with the token, and without one nothing is sent (173.72529ms)
✔ an announcement that fails is a warning, never a failed deploy (1.76624ms)
✔ the stages run inside the window: started before, finished after, even when they throw; a dry run says nothing (2.17855ms)
✔ deploy.mjs announces every deploy, and the workflow passes it the token (1.09087ms)
ℹ tests 61
ℹ suites 0
ℹ pass 60
ℹ fail 0
ℹ cancelled 0
ℹ skipped 1
ℹ todo 0
ℹ duration_ms 9473.52674
